Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge upstream changes #1

Open
wants to merge 197 commits into
base: master
Choose a base branch
from

Conversation

jschoewe
Copy link

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

bishopbm1 and others added 30 commits May 23, 2022 10:24
Update Python package name to python instead of python2, and use file install
vs. package install by default

Partially rolls back #654, though continues to allow the user to set the
package via $rabbitmqadmin_package
- Update existing tests to include the leading spaces and some
  additional formatting
- Add new test case for the newer format included in `rabbitmqctl -q
  status` that's included in RabbitMQ >= v3.8.x, originally fixed in
  #814

See discussion in #872
Update tests for rabbitmqctl version parsing
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when
enumerating enabled plugins.  Starting with rabbitmq 3.10, this command
will output a informational message:
'Listing plugins with pattern ".*" ...' which can be hidden with the -s
or -q parameter.  However, this approach will break rabbitmq_plugin on
older versions of RabbitMQ.

This patch implements a workaround that simply ignores the outputted line
if it exists.

Fixes: #909
Make rabbitmq_plugin resource functional on RabbitMQ 3.10.x
Minor fix to resolve a linting check
Enable usage of custom list of plugins when using static config file
When overriding local node name (using NODENAME environment variable),
clustering does not work as tinit_node is tested again hostname or
fqdn. By adding the optional local_node to specify which node is the
current node we can fix this issue.

Use case: a server with a public and a private interface, rabbitmq
cluster nodes communicates through the private interface while hostname
and fqdn resolves to the public interface (and that can't be changed
because of other dependencies on the server). The only solution is to
use dedictated name for the private interface.
This fixes inconsistent logic to determine management ip address if
the rabbitmq::management_ip_address parameter is not set, and makes
sure all logic tries to look up the rabbitmq::node_ip_address
parameter.
Fix detection of management_ip_address for rabbitmqadmin
wyardley and others added 30 commits September 16, 2024 13:27
* Require package_apt_pin to be a non-empty string or number
* Use `nil` instead of empty string in test for empty pin
- Add hosts entry for `foobar` in acceptance test step (resolves issue
  that was causing rabbitmq not to start)
- Switch `rabbitmq::cluster[:local_node]` to have `catch_failures =
  true` vs `expect_failures = true`
Disallow empty string in `package_apt_pin`
…nt plugin (#1024)

Add ssl options for client renegotiation to rabbitmq-server

---------

Co-authored-by: kperronne <[email protected]>
Drop support for Debian 10, Ubuntu 18, and FreeBSD 12
Improve test coverage in main class spec
- Remove support for CentOS / RHEL 7 (breaking change)
- Remove workarounds specific to EPEL and require_epel parameter (breaking change)
- Add support for CentOS / RHEL 9 in metadata
- Where repos_ensure is not set, install centos-release-rabbitmq-38 to
  support installing RabbitMQ from semi-official source
- Add in some additional tests for coverage (followup to #1028) that
  were hard to test without a supported RedHat family OS in metadata

Fixes #816

Signed-off-by: William Yardley <[email protected]>
Add support for CentOS / RHEL 9 and drop support for 7
…Default undef all of them so it does nothing unless you enable.
Signed-off-by: William Yardley <[email protected]>
Add an `enable_centos_release` parameter, defaulting to `false`, except
on CentOS, where it defaults to `true`. If enabled on any OS in the
RedHat family when `repos_ensure` is also disabled, it controls adding
the `centos-release-rabbitmq` package (currently
`centos-release-rabbitmq-38`)

Fixes #1033
Closes #1032
Signed-off-by: William Yardley <[email protected]>
…fully dependent on an enablement variable now, with tests to verify that behavior.
Add quorum queue auto-reconciliation parameter support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.